Skip to content

Clarify Copilot rate limit troubleshooting guidance#44545

Merged
Sharra-writes merged 2 commits into
github:mainfrom
ded-furby:copilot-rate-limit-guidance-43998
Jun 12, 2026
Merged

Clarify Copilot rate limit troubleshooting guidance#44545
Sharra-writes merged 2 commits into
github:mainfrom
ded-furby:copilot-rate-limit-guidance-43998

Conversation

@ded-furby

@ded-furby ded-furby commented Jun 1, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Summary

  • update the rate-limit troubleshooting text so it no longer assumes every client shows a retry timestamp
  • document that the message may instead tell people to wait for reset or upgrade for additional usage
  • keep the article linked to the usage-limits guidance for next steps

Closes #43998
Closes #44558
Closes #44559

Validation

  • git diff --check
  • content-only review of content/copilot/how-tos/troubleshoot-copilot/troubleshoot-common-issues.md
  • I did not run the full docs content linter in this temporary sparse checkout

@github-actions github-actions Bot added the triage Do not begin working on this issue until triaged by the team label Jun 1, 2026
@github-actions

github-actions Bot commented Jun 1, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source Review Production What Changed
copilot/how-tos/troubleshoot-copilot/troubleshoot-common-issues.md fpt
ghec
 fpt
ghec

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

@ahmedrocky55436-stack

This comment was marked as spam.

Sign in to view
jobayerbt
jobayerbt reviewed Jun 2, 2026
View reviewed changes

@jobayerbt jobayerbt left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixes #44558

jobayerbt
jobayerbt reviewed Jun 2, 2026
View reviewed changes

@jobayerbt jobayerbt left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixes #44559

@Sharra-writes

Sharra-writes commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

@ded-furby Yeah, I'll take this. I think it's a reasonable update. If my tests ever complete...

@Sharra-writes Sharra-writes added this pull request to the merge queue Jun 12, 2026
Merged via the queue into github:main with commit d9b52eb Jun 12, 2026
41 checks passed
@github-actions

github-actions Bot commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@Sharra-writes Sharra-writes Sharra-writes approved these changes

+1 more reviewer

@jobayerbt jobayerbt jobayerbt left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

triage Do not begin working on this issue until triaged by the team

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Interoperability Test 101.000.060226 Clarify rate limit error message and actions

4 participants

@ded-furby @ahmedrocky55436-stack @Sharra-writes @jobayerbt